src/pages/Tracker/Tracker.tsx (2)

104-115: Make filtering more explicit and robust; also verify data source populates merged_at.

Some GitHub endpoints don’t include pull_request.merged_at unless you fetch PR details. If merged_at is missing, “merged” will show empty. Refactor to a switch and keep semantics unchanged.

Apply within this range:

-      filtered = filtered.filter((item) => {
-        if (filterType === "merged") {
-          return !!item.pull_request?.merged_at
-        }
-        else if (filterType === "closed") {
-          return item.state === "closed" && !item.pull_request?.merged_at
-        }
-        else {
-          //open
-          return item.state === "open"
-        }
-      });
+      filtered = filtered.filter((item) => {
+        switch (filterType) {
+          case "merged":
+            return Boolean(item.pull_request?.merged_at);
+          case "closed":
+            return item.state === "closed" && !item.pull_request?.merged_at;
+          case "open":
+            return item.state === "open";
+          default:
+            return true;
+        }
+      });

Optionally, narrow the filter type to prevent invalid values elsewhere:

type StateFilter = "all" | "open" | "closed" | "merged";

To verify data shape, please confirm your fetch layer sets pull_request.merged_at for PRs (e.g., GraphQL or pulls.get). If you want, I can generate a script to scan the repo for where merged_at is sourced.

---

81-87: Effect dependencies don’t match the comment; either include username (and fetchData) or fix the comment.

As written, the effect won’t re-fetch on username change. If that’s intended, update the comment. If not, include deps.

-  // Fetch data when username, tab, or page changes
-  useEffect(() => {
+  // Fetch data when username, tab, or page changes
+  useEffect(() => {
     if (username) {
       fetchData(username, page + 1, ROWS_PER_PAGE);
     }
-  }, [tab, page]);
+  }, [username, tab, page, fetchData]);

If fetchData isn’t stable, wrap it with useCallback in the hook or suppress the dep intentionally and update the comment to avoid confusion.

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.